Authorization flow initiation using short-term wireless communication

ABSTRACT

In general, aspects of the disclosure are directed towards techniques for initiating an authorization flow with a user to enable a user interface-limited client computing device to obtain access to protected resources hosted by a resource service. In some aspects, a computing device comprises at least one processor. The computing device also comprises a short-range wireless communication module operable by the at least one processor to receive, using short-range wireless communication, an authentication request from a client device. The computing device also comprises an authorization module operable by the at least one processor to receive authorization to provide at least one security credential to the client device, wherein the authorization module is further configured to, responsive to receiving the authorization, send an indication of the authorization to an authentication service.

RELATED APPLICATION

This application is a Continuation of U.S. application Ser. No.13/837,062, filed Mar. 15, 2013, which claims the benefit of U.S.Provisional Patent Application No. 61/761,202, filed Feb. 5, 2013, theentire content of each of which is incorporated herein by reference.

BACKGROUND

Authorization frameworks and protocols have been developed to enable athird-party application to obtain limited access to a Hyper-TextTransfer Protocol (HTTP) service, either on behalf of a resource ownerby orchestrating an approval interaction between the resource owner andthe HTTP service, or by allowing the third-party application to obtainaccess on its own behalf.

In one such framework known as OAuth 2.0, an authorization serviceaccepts requests from a client to access resources controlled by theresource owner and hosted by a resource service. The authorizationservice issues a set of credentials to the client that is different thanthat of the resource owner in order to allow the client to access theresources without having access to the resource owner credentials.However, OAuth 2.0 is directed to clients that are offered as networkservices and are, as a result, able to present extensive user interfacesto the resource owner in response to initiation, by the resource owner,of an authorization flow.

SUMMARY

In one example, the disclosure is directed to a method. The method mayinclude receiving, by a computing device and using short-range wirelesscommunication, an authentication request from a client device. Themethod may also include receiving, at an input device operably coupledto the computing device, authorization to provide at least one securitycredential to the client device. The method may further include,responsive to receiving the authorization, sending, by the computingdevice and to an authentication service, an indication of theauthorization.

In another example, the disclosure is directed to a computer-readablestorage medium encoded with instructions that, when executed by at leastone processor of a computing device, cause the at least one processor toperform operations comprising establishing, by the computing device andwith a client device, radio communication for short-range wirelesscommunication. The operations may also comprise receiving, by thecomputing device and using short-range wireless communication, anauthentication request from a client device. The operations may furthercomprise receiving, by the computing device, authorization to provide atleast one security credential to the client device. The operations mayalso comprise responsive to receiving the authorization, sending, by thecomputing device and to an authentication service, an indication of theauthorization.

In another example, the disclosure is directed to a computing devicecomprising at least one processor, a short-range wireless communicationmodule operable by the at least one processor to receive, usingshort-range wireless communication, an authentication request from aclient device, and an authorization module operable by the at least oneprocessor to receive authorization to provide at least one securitycredential to the client device, wherein the authorization module isfurther configured to, responsive to receiving the authorization, sendan indication of the authorization to an authentication service.

In another example, the disclosure is directed to a method comprisingsending, by a client device and using short-range wirelesscommunication, an authentication request to a computing device. Themethod may also comprise receiving, by the client device and responsiveto the authentication request, at least one security credential thatprovides the client device with access to exchange information with aresource service that hosts a protected resource associated with the atleast one security credential.

The details of one or more aspects of the disclosure are set forth inthe accompanying drawings and the description below. Other features,objects, and advantages of the disclosure will be apparent from thedescription and drawings, and from the claims.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is a block diagram illustrating an example system havingcomputing devices configured to enable a client device to obtain accessto resources according to some aspects of the present disclosure.

FIGS. 2A-2B depict block diagrams illustrating further details of anexample authorization flow initiated by a client device according totechniques described in this disclosure.

FIG. 3 is a block diagram illustrating further details of one example ofa client device configured according to one or more techniques of thepresent disclosure.

FIG. 4 is a block diagram illustrating further details of one example ofa computing device configured according to one or more techniques of thepresent disclosure

FIGS. 5A-5C depict a flow chart illustrating an example process that maybe performed by a computing system to authorize a client device toaccess resources owned by a user and served by a resource service,according to techniques of the present disclosure.

FIG. 6 is a flow chart illustrating an example process that may beperformed by a computing system to authorize a client device to accessresources owned by a user and served by a resource service, according totechniques of the present disclosure.

DETAILED DESCRIPTION

In general, aspects of the disclosure are directed towards techniquesfor initiating an authorization flow with a user to enable a userinterface-limited client computing device to obtain access to protectedresources hosted by a resource service.

Some client computing devices (hereinafter, “client devices”), such asprinters, fax machines, telephones, video-game consoles, televisionset-top boxes, credit card terminals, automatic teller machines, vendingmachines, and sales/information kiosks have limited user-interfaces thatdo not provide expansive input and output devices such as keyboards,whether real or virtual, and web browsers. Some client devices may havesuch expansive input and output devices, but users may find theuser-interfaces unwieldy or otherwise difficult to use outside of anarrow range of activities. In addition, many client devices such asthose listed above may be shared among multiple users as part of ashared workspace (e.g., office printers) or may be located in a publicarea to the public at-large, which exposes the client devices and anydata stored thereon, however fleetingly, to hacking. For example,requiring a user to enter security credentials directly into a sharedclient device may create security problems, such as another personlooking over the user's shoulder or even looking at the shared clientdevice display, if the shared client device display displays thesecurity credentials as the user enters that information. Likewise,entering security credentials directly into the shared client device mayalso introduce unknowns, such as if the security credentials are beingstored by the shared client device and, if so, the security employed bythe shared client device to protect the stored security credentials fromauthorized acquisition.

Techniques of this disclosure may, in various aspects, enable a clientdevice to initiate an authorization flow with a user and to send anauthorization request for the authorization flow to a mobile computingdevice of the user when the mobile computing device, such as a mobilephone, is within a defined range of a tag device of the client device.The tag device may be a near-field communication (NFC) tag, for example.The user may engage the client device to perform one or more operationsthat require access to resources owned by the user but provided by aresource service that requires an indication of user authorizationbefore permitting access to the resources. To initiate the authorizationflow, the client device may prompt the user, by a user-interface of theclient device, to locate the mobile computing device within the definedrange of the tag device in order to engage the tag device. In someaspects, locating the mobile computing device within the defined rangeof the tag device may include tapping the tag device with the mobilecomputing device. Once the mobile computing device is located within thedefined range of the tag device, the client device may send anauthorization request for the authorization flow to the mobile computingdevice using short-range wireless communication provided by the devicetag, and the user may grant authorization to the client device using aninput device of the mobile computing device. The authorization flowdescribed herein may conform, at least in part, to OAuth 2.0, whichdefines an authorization framework to enable third-party applications toobtain limited access to a Hypertext Transfer Protocol (HTTP) service byorchestrating an approval interaction between a resource owner and theHTTP service. However, the techniques are not limited to the OAuth 2.0authorization framework context.

The mobile computing device may continue the authorization with anauthorization service associated with the resource service. Theauthorization service may generate a security credential, such as anaccess token, that provides an indication of authorization for the user.The authorization service may provide the access token directly to theclient device by a network connection. Alternatively, the mobilecomputing device may relay the access token from the authorizationservice to the client device by exchanging the access token with the tagdevice using short-range wireless communication.

The techniques of this disclosure may provide one or more advantages.For example, despite user interface limitations of the client device,utilizing the mobile computing device to receive and grant anauthorization request may enable convenient authorization of the clientdevice to permit access by the client device to user resources providedby a resource service. As another example, because the user of themobile computing device may authenticate directly with the resourceservice and authenticate indirectly with the client device using anaccess token, the user may avoid sending user credentials to apotentially insecure client device. As another example, unless the userrevokes access to the client device, the mobile computing device neednot request authorization each time the user seeks to use servicesprovided by the client device. Instead, by again engaging the tag devicewith the mobile computing device, new security credentials mayautomatically be generated and sent to the client device.

FIG. 1 is a block diagram illustrating an example system havingcomputing devices configured to enable a client device to obtain accessto resources according to some aspects of the present disclosure. In theillustrated aspect, computing system 10 includes client device 110 thatis configured to initiate an authorization flow with a user of clientdevice 110. Client device 110 may represent printers, fax machines,telephones, video-game consoles, television set-top boxes, credit cardterminals, automatic teller machines, vending machines, andsales/information kiosks. A user 132 of computing device 100 may operateclient device 110 to use services provided by client device 110, such asprinting, scanning, or faxing a document, making a bank withdrawal,purchasing and receiving vended items, and so forth.

Computing system 10 also includes computing device 100, which mayrepresent a mobile computing device, including but not limited to amobile phone, a tablet computer, a personal digital assistant, ahandheld computer, a media player, and the like, including a combinationof two or more of these items. Computing device 100 includes display102, such as a presence-sensitive display, that may receive input andprovide output.

Client device 110 includes a user interface device 112 that presents aprompt 116 to the user in order to initiate the authorization flow. Userinterface device 112 may represent a liquid crystal display (LCD)device, a presence-sensitive display, another visual display device, alight-emitting diode (LED) or other light, a speaker, any other type ofdevice that can generate intelligible output to a user. User interfacedevice 112 may provide limited user interface capabilities. For example,user interface device 112 may provide neither a physical nor virtualkeyboard. In addition, user interface device 112 may provide only alimited number of visualizations statically-defined within aconfiguration of client device 110 and may not provide rendering andinput capabilities associated with a web browser, for instance. In someaspects, client device 110 does not provide a web browser.

Prompt 116 may represent words or other glyphs presented by userinterface device 112, activation of an LED represented by user interfacedevice 112, or a sound prompt or voice request from a speakerrepresented by user interface device 112, for instance. Prompt 116prompts the user of computing device 100 to locate, using motion 105,computing device 100 within the defined range of tag device 114 ofclient device 110 in order to establish radio communication with (or“engage”) tag device 114.

Responsive to prompt 116, the user may, if inclined, locate computingdevice 100 within the defined range of tag device 114, which causescomputing device 100 to engage tag device 114 using communicationpathway 126. In some aspects, communication pathway 126 may include ashort-range communication pathway, such as near-field communication(NFC), between tag device 114 and computing device 100. Tag device 114may represent a short-range communication device affixed to or otherwiseassociated with client device 110 to enable client device 110 tocommunicate using short-range communication. For example, tag device 114may represent a near-field communication (NFC) tag, a Bluetoothtransceiver, or a Bluetooth low energy transceiver.

Computing device 100 may include a short-range communication module,such as a near-field communication (NFC) module (not shown) capable ofshort range wireless communication via communication pathway 126 withtag device 114 associated with client device 110 over a short distance.For example, this short distance may be less 100 meters, less than 10meters, less than 1 meter, less than 10 centimeters, less than 5centimeters, or even less than 4 centimeters. Although only one tagdevice 114 is illustrated in the example of FIG. 1, tag device 114 maybe representative of any number of tag devices configured to communicatewith computing device 100 using a short range communication protocol,such as an NFC protocol. Since each tag device 114 may be relativelysimple and configured to communicate with any number of other NFCdevices, computing device 100 may be capable of establishingcommunication with thousands or even millions of different clientdevices. In some examples, communication pathway 126 may include an NFCnetwork.

Client device 110 is further configured to provide authorization request130 for the authorization flow to computing device 100 usingcommunication pathway 126. Authorization request 130 represents arequest for authorization to exchange information with a service.Authorization request 130 may include an identifier for client device110, a requested scope for the requested authorization, local state,and/or a redirection Uniform Resource Identifier (URI) to whichauthorization service 122 may redirect mobile computing device 100 upongranting access to resource service 120. In this aspect, client device110 sends authorization request 130 directly to computing device 100 bycommunication pathway 126.

Computing device 100, in response to receiving authorization request130, may display prompt 104 that provides user 132 of computing device110 with the option to accept or deny authorization request 130. In theillustrated example, prompt 104 includes accept button 106 and rejectbutton 108, which user 132 may press to accept or reject, respectfully,authorization request 130. Prompt 104 may represent an input interfaceof an application, executing on computing device 100, that is configuredto recognize authorization request 130 as a request for authorization toexchange information with a service. The application may be provided byan entity that manufactures client device 110 or software operating onclient device 110. Alternatively, the application may be a utilityprovided by an entity that manufactures computing device 100 or softwareoperating on computing device 100.

In some aspects, prompt 104 may include an input screen, such as a webpage presented by a web browser of computing device 100, to request user132 to provide resource owner credentials, such as a username andpassword. The web page may be identified by a URI associated withauthorization service 122. For example, the web page may represent agrant access page or authorization endpoint associated withauthorization service.

If user 132 rejects authorization request 130, computing device 100 mayterminate the authorization flow. If user 132 accepts authorizationrequest 130, computing device 100 continues the authorization flow bygranting authorization request 130 in conjunction with authorizationservice 122. Computing device 100 and authorization service 122communicate using communication pathway 128, which may represent, forinstance, a short-range communication pathways such as Bluetooth orradio-frequency identification (RFID), active NFC communication, widearea networks (WANs), local area networks (LANs), a mobile serviceprovider network (e.g., a 3G or Long-Term Evolution (LTE) network), andthe like. Example authorization flows for granting authorization request130 are described below with respect to FIG. 5.

Authorization service 122 represents a service role for theauthorization flow, provided by remote system 118, to authenticate anowner of a protected resource (i.e., a “resource owner”) hosted byresource service 120 and to authorize client device 110 to access theprotected resource according to a requested scope. Authorization service122 issues a security credential for use by client device 110 aftersuccessfully authenticating user 132 and authorizing client device 110.The security credential provides client device 110 with access toexchange information with resource service 120 that hosts a protectedresource associated with the security credential and with user 132. Thesecurity credential provided by authorization service 122 may include anaccess token.

An access token includes data defining a specific scope and, in someaspects, lifetime for an authorized request and may be used by clientdevice 110 to obtain access to protected resources that are hosted byresource service 120 and owned or otherwise associated with user 132. Inother words, an access token represents credential to access protectedresources and defines a specific scope and, in some aspects, duration ofaccess that is granted by the resource owner and is enforced byauthorization service 122 and resource service 120.

An access token may include an identifier usable to retrieveauthorization information or may include the authorization informationin a secure, verifiable format, e.g., a token string consisting of dataand cryptographic signature. Access tokens may, in various aspects, havedifferent formats, structures, and methods of utilization according toresource service 120 security requirements. In some aspects, additionalauthentication credentials may be needed in order for client device 110to use an access token. Consequently, an access token may be used inaccordance with techniques described herein to replace differentauthorization credentials (e.g., a username and password combination)with a single token usable to access resource service 120, which enablesissuing an access token that is more restrictive than the authorizationgrant used to obtain the access token, as well as providing a singlemechanism for authorization to resource service 120.

Resource service 120 hosts protected resources owned by user 132. Theprotected resources may include any digital information or hostedresources associated with user 132, such as digital images, digitalvideos, digital music, eBooks, email accounts, financial information, acloud storage account, a video game profile, a social network profile,and user preferences, for instance. Resource service 120 may present anapplication programming interface (API) to provide access to protectedresources.

As a result of the authorization flow initiated by client device 110,client device 110 receives an access token, issued by authorizationservice 122, that corresponds to authorization request 130. Clientdevice 110 uses communication pathway 124 to present the access token toresource service 120 to access protected resources in accordance withthe scope of the access token. For example, client device 110 may accessand download photos owned by user 132, access a cloud storage account ofuser 132 to upload digital files such as scanned documents, or otherwiseaccess and use the protected resources associated with user 132.Communication pathway 124 may represent any of the example communicationpathways described above with respect to communication path 128.

Upon completing a transaction using the access token, client device 110may immediately delete the access token, wait for the access token toexpire, and/or communicate with user 132 to provide user 132 with anoption to delete the access token if desired.

In some aspects, authorization service 122 may issue a refresh tokencorresponding to authorization request 130. Client device 110 may usethe refresh token as a credential to authorization service 122 to obtaina fresh access token when either a current access token corresponding toauthorization request 130 becomes invalid or expires or to obtain one ormore additional access tokens with additional or narrower scope (e.g.,having a shorter lifetime or fewer authorized permissions).

Remote system 118 may include but is not limited to one or more remoteservers, one or more computing devices, and/or a cloud computingservice. A cloud computing service may include one or more remoteservers that may provide one or more services, including but not limitedto computation, software, data access, and storage services, withoutrequiring end-user knowledge of the physical location and configurationof the systems that deliver the one or more services. Resource service120 and authorization service 122 may be hosted by the same or differentdevices, e.g., servers, of remote system 118. In some aspects, resourceservice 120 and authorization service 122 may be hosted by differentremote systems administered by separate entities.

In some aspects, user 132 may opt-out of third-party authorizationfeatures provided by resource service 120. In some aspects, thethird-party authorization features provided by resource service 120 aredisabled by default and user 132 must opt-in in order to enable thesefeatures.

FIG. 2A is a block diagram illustrating further details of an exampleauthorization flow initiated by a client device according to techniquesdescribed in this disclosure. The example authorization flow isdescribed in the context of computing system 10 of FIG. 1. Communicationpathways 124, 128 have been removed to simplify illustration.

In this example, client device 110 is configured to provideauthorization request 130 for the authorization flow to computing device100 using communication pathway 126 to computing device 100. Computingdevice 100, in response to receiving authorization request 130, maydisplay prompt 104 that provides user 132 of computing device 110 withthe option to accept or deny authorization request 130. User 132 acceptsauthorization request 130, and computing device 100 continues theauthorization flow by issuing authorization grant 400, corresponding toauthorization request 130, to authorization service 122. Authorizationgrant 400 may include a credential representing authorization by theresource owner (e.g., user 132) to access protected resources associatedwith the resource owner. Authorization grant 400 may be usable to obtainan access token. In this sense, authorization grant 400 also representsa request for an access token.

In some aspects, authorization grant 410 may include resource ownercredentials of user 132, such as a username and password of user 132.Computing device 100 may store the resource owner credentials topersistent storage and present the resource owner credentials toauthorization service 122 in authorization grant 400. In some aspects,authorization service 122 and computing device 100 engage in a separateauthentication protocol. For instance, responsive to receivingauthorization grant 400, authorization service 122 may send a requestfor resource owner credentials to computing device 100. In response,computing device 100 may display, using a web browser or otherapplication, a login or other authentication screen by which user 132may enter and submit his or her resource owner credentials toauthorization service 122.

Authorization service 122 authorizes the resource owner credentials and,if the resource owner credentials are valid, issues access token 402 tocomputing device 100. In this way, computing device 100 stands in forclient device 110 during the authorization grant/access token exchangeand resource owner credentials of user 132 need not be shared withclient device 110.

Computing device 100 receives access token 402 and sends, responsive toauthorization request 130, access token 402 to client device 110.Computing device 100 may associate access token 402 with authorizationrequest 130 in a message to client device 110. In some aspects,computing device 100 may, upon receiving token 402 from authorizationservice 122, prompt user 132 to again locate computing device 100 withina defined range of tag device 114 to send token 402 using communicationpathway 126. In some aspects, computing device 100 sends access token402 to client device 110 by a different communication pathway, such as aLAN.

Client device 110 receives access token 402 and presents token 402 toresource service 120 with a request for a protected resource. Resourceservice 120 validates access token 402 and, if valid, serves protectedresource. In some instances, client device 110 refreshes access token402 with a refresh token provided by authorization service 122.

FIG. 2B is a block diagram illustrating further details of an exampleauthorization flow initiated by a client device according to techniquesdescribed in this disclosure. The example authorization flow isdescribed in the context of computing system 10 of FIG. 1. Communicationpathways 124, 128 have been removed to simplify illustration.

In this example, client device 110 is configured to provideauthorization request 130 for the authorization flow to computing device100 using communication pathway 126 to computing device 100. Computingdevice 100, in response to receiving authorization request 130, maydisplay prompt 104 that provides user 132 of computing device 110 withthe option to accept or deny authorization request 130. User 132 acceptsauthorization request 130, and computing device 100 continues theauthorization flow by issuing authorization grant 410, corresponding toauthorization request 130, to authorization service 122. Authorizationgrant 410 may include a credential representing authorization by theresource owner (e.g., user 132) to access protected resources associatedwith the resource owner. Authorization grant 410 may be usable to obtainan access token. In this sense, authorization grant 410 also representsa request for an access token.

In some aspects, as described above with respect to FIG. 2A,authorization grant 410 may include resource owner credentials of user132, such as a username and password. Computing device 100 may store theresource owner credentials to persistent storage and present theresource owner credentials to authorization service 122 in authorizationgrant 410. In some aspects, authorization service 122 and computingdevice 100 engage in a separate authentication protocol. For instance,responsive to receiving authorization grant 410, authorization service122 may send a request for resource owner credentials to computingdevice 100. In response, computing device 100 may display, using a webbrowser or other application, a login or other authentication screen bywhich user 132 may enter and submit his or her resource ownercredentials to authorization service 122.

Authorization service 122 authorizes the resource owner credentials and,if the resource owner credentials are valid, issues access token 412(and optionally a refresh token) directly to client device 110 usingcommunication pathway 124. In this way, computing device 100 stands infor client device 110 during the authorization grant step of theauthorization flow, but authorization service 122 sends access token 412directly to client device 110. As a result, resource owner credentialsof user 132 need not be shared with client device 110.

In some aspects, authorization request 130 may include a redirection URIpreviously provided to client device 110 by authorization service 122.In such aspects, client device 110 may direct computing device 100 toauthorization service 122 using the redirection URI. Using resourceowner credentials provided in authorization grant 410, authorizationservice 122 authorizes the resource owner credentials and, if theresource owner credentials are valid, issues access token 412 directlyto client device 110 using communication pathway 124. Again, computingdevice 100 stands in for client device 110 during the authorizationgrant step of the authorization flow, but authorization service 122sends access token 412 directly to client device 110. As a result,resource owner credentials of user 132 need not be shared with clientdevice 110. In some instances, prior to and as a prerequisite to issuingaccess token 412 directly to client device 110, authorization service122 issues redirect message 416, which includes an authorization codethat is associated with access token 412. Computing device 100 providesthe authorization code to client device 110, which presents theauthorization code to authorization service 122 in order to receiveaccess token 412. Authorization service 122 may additionally authorizeclient device 110 as a prerequisite to issuing access token 412 (andoptionally a refresh token) directly to client device 110.

FIG. 3 is a block diagram illustrating further details of one example ofa client device shown in FIGS. 1, 2A, and 2B, in accordance with one ormore techniques of the present disclosure. FIG. 3 illustrates only oneparticular example of client device 110, and other examples of clientdevice 110 may be used in other instances. Although shown in FIG. 3 as astand-alone client device 200 for purposes of example, a client devicemay be any component or system that includes one or more processors orother suitable computing environment for executing software instructionsand, for example, need not necessarily include one or more elementsshown in FIG. 3.

As shown in the specific example of FIG. 3, client device 200 includesone or more processors 202, one or more input devices 204, one or morecommunication units 206, one or more output devices 212, one or morestorage devices 208, user interface (UI) device 210, and tag device 228.Client device 200, in one example, further includes UI device module218, tag device interface module 220, resource service interface module,authorization service interface module 224, one or more applications226, and operating system 216 that are executable by computing device300. Each of components 202, 204, 206, 208, 210, 212, and 226 arecoupled (physically, communicatively, and/or operatively) forinter-component communications. In some examples, communication channels214 may include a system bus, a network connection, an inter-processcommunication data structure, or any other method for communicatingdata. As one example in FIGS. 3, 202, 204, 206, 208, 210, 212, and 226may be coupled by one or more communication channels 214. User interfacedevice module 218, tag device interface module 220, resource serviceinterface module 222, authorization service interface module 224, andthe one or more applications 226 may also communicate information withone another as well. While illustrated as separate modules, any one ormore of modules 218, 220, 222, and 224 may be implemented as part of anyof applications 226.

Processors 202, in one example, are configured to implementfunctionality and/or process instructions for execution within clientdevice 200. For example, processors 202 may be capable of processinginstructions stored in one or more storage devices 208. Examples ofprocessors 202 may include, any one or more of a microprocessor, acontroller, a digital signal processor (DSP), an application specificintegrated circuit (ASIC), a field-programmable gate array (FPGA), orequivalent discrete or integrated logic circuitry.

One or more storage devices 208 may be configured to store informationwithin client device 200 during operation. Storage device 208, in someexamples, is described as a computer-readable storage medium. In someexamples, storage device 208 is a temporary memory, meaning that aprimary purpose of storage device 208 is not long-term storage. Storagedevice 208, in some examples, is described as a volatile memory, meaningthat storage device 208 does not maintain stored contents when thecomputer is turned off. Examples of volatile memories include randomaccess memories (RAM), dynamic random access memories (DRAM), staticrandom access memories (SRAM), and other forms of volatile memoriesknown in the art. In some examples, storage device 208 is used to storeprogram instructions for execution by processors 202. Storage device208, in some examples, is used by software or applications running onclient device 200 to temporarily store information during programexecution.

Storage devices 208, in some examples, also include one or morecomputer-readable storage media. Storage devices 208 may be configuredto store larger amounts of information than volatile memory. Storagedevices 208 may further be configured for long-term storage ofinformation. In some examples, storage devices 208 include non-volatilestorage elements. Examples of such non-volatile storage elements includemagnetic hard discs, optical discs, floppy discs, flash memories, orforms of electrically programmable memories (EPROM) or electricallyerasable and programmable (EEPROM) memories.

Client device 200, in some examples, also includes one or morecommunication units 206. Client device 200, in one example, utilizescommunication unit 206 to communicate with external devices via one ormore networks, such as one or more wireless networks. Communication unit206 may be a network interface card, such as an Ethernet card, anoptical transceiver, a radio frequency transceiver, or any other type ofdevice that can send and receive information. Other examples of suchnetwork interfaces may include Bluetooth, 3G and WiFi radios computingdevices as well as Universal Serial Bus (USB). In some examples, clientdevice 200 utilizes communication unit 206 to wirelessly communicatewith an external device such as a server (e.g., remote system 118 ofFIGS. 1, 2A, and 2B).

In addition, the client device 200 may include tag device 228 forshort-range wireless communication. As described herein, tag device 228may be active hardware that is configured to communicate with othershort-range communication devices. In general, tag device 228 may beconfigured to communicate wirelessly with other devices in physicalproximity to tag device 228 (e.g., less than approximately tencentimeters, or less than approximately four centimeters). In someexamples, tag device 228 may include a near-field communication (NFC)device that communicates via NFC. In other examples tag device 228 maybe replaced with an alternative short-range communication deviceconfigured to communicate with and receive data from other short rangecommunication sensors. These alternative short-range communicationdevices may operate according to Bluetooth, Bluetooth Low Energy,Ultra-Wideband radio, or other short-range wireless communicationprotocols. In some examples, tag device 228 may be an external hardwaredevice that is coupled with client device 200 via a bus (such as via aUniversal Serial Bus (USB) port). Tag device 228, in some examples, mayalso include software which may, in some examples, be independent fromoperating system 216, and which may, in some other examples, be asub-routine of operating system 216 or more specifically of tag deviceinterface module 220. In some examples, tag device interface module 220may provide an interface to send and receive short-range wirelesscommunications using tag device 228 to, e.g., initiate an authorizationflow with a computing device and/or to receive an access token from acomputing device.

Client device 200 may also include one or more input devices 204. Inputdevice 204 is configured to receive input. Examples of input device 304include a scanner, a fax machine, and an infrared interface.

One or more output devices 212 may also be included in client device200. Output device 212, in some examples, is configured to provideoutput to a user using tactile, audio, or video stimuli. Output device212, in one example, includes a presence-sensitive display, a soundcard, a video graphics adapter card, or any other type of device forconverting a signal into an appropriate form understandable to humans ormachines. Additional examples of output device 212 include a speaker, acathode ray tube (CRT) monitor, a liquid crystal display (LCD), or anyother type of device that can generate intelligible output to a user.

In some examples, UI device 210 may include functionality of inputdevice 204 and/or output device 212. UI device 212 may be apresence-sensitive display. User interface device 212 may providelimited user interface capabilities. For example, user interface device212 may provide neither a physical nor virtual keyboard. In addition,user interface device 212 may provide only a limited number ofvisualizations statically-defined within a configuration of clientdevice 200 and may not provide rendering and input capabilitiesassociated with a web browser, for instance. In some aspects, clientdevice 200 does not provide a web browser for interfacing with a user.User interface device module 218 may control, at least in part, theoperations of user interface device 210 and interface user interfacedevice 210 to, e.g., application 226.

Client device 200 may include operating system 216. Operating system216, in some examples and at least in part, controls the operation ofcomponents of client device 200. For example, operating system 216, inone example, facilitates the communication of user interface devicemodule 218 with processors 202, communication unit 206, storage device208, input device 204, user interface device 210, tag device 228, andoutput device 212.

In some examples, resource service interface module 222 provides anapplication programming interface to application 226 for interfacingwith a resource service, such as resource service 120 of FIGS. 1, 2A,and 2B. In some examples, authorization service interface module 224provides an application programming interface to application 226 forinterfacing with an authorization service, such as resource service 122of FIGS. 1, 2A, and 2B.

UI device module 218, tag device interface module 220, resource serviceinterface module 222, authorization service interface module 224, andone or more applications 226 may include program instructions and/ordata that are executable by client device 200. As one example, each ofcomponents 218, 220, 222, 224, and 226 may include instructions thatcause client device 200 to perform one or more of the operations andactions described in the present disclosure.

FIG. 4 is a block diagram illustrating further details of one example ofa computing device shown in FIGS. 1, 2A, and 2B, in accordance with oneor more techniques of the present disclosure. FIG. 4 illustrates onlyone particular example of computing device 100, and other examples ofcomputing device 100 may be used in other instances. Although shown inFIG. 4 as a stand-alone computing device 300 for purposes of example, acomputing device may be any component or system that includes one ormore processors or other suitable computing environment for executingsoftware instructions and, for example, need not necessarily include oneor more elements shown in FIG. 4 (e.g., input devices 304, userinterface devices 310, output devices 312).

As shown in the specific example of FIG. 4, computing device 300includes one or more processors 302, one or more input devices 304, oneor more communication units 306, one or more output devices 312, one ormore storage devices 308, and user interface (UI) device 310, andshort-range wireless communication device 236. Computing device 300, inone example, further includes UI device module 318, authorization module320, one or more applications 322, and operating system 316 that areexecutable by computing device 300. Each of components 302, 304, 306,308, 310, 312, and 326 are coupled (physically, communicatively, and/oroperatively) for inter-component communications. In some examples,communication channels 314 may include a system bus, a networkconnection, an inter-process communication data structure, or any othermethod for communicating data. As one example in FIG. 4, components 302,304, 306, 308, 310, 312, and 326 may be coupled by one or morecommunication channels 314. UI device module 318, authorization module320, and one or more applications 322 may also communicate informationwith one another as well as with other components in computing device300. While illustrated as separate modules, any one or more of modules318 or 320 may be implemented as part of any of applications 322.

Processors 302, in one example, are configured to implementfunctionality and/or process instructions for execution within computingdevice 300. For example, processors 302 may be capable of processinginstructions stored in storage device 308. Examples of processors 302may include, any one or more of a microprocessor, a controller, adigital signal processor (DSP), an application specific integratedcircuit (ASIC), a field-programmable gate array (FPGA), or equivalentdiscrete or integrated logic circuitry.

One or more storage devices 308 may be configured to store informationwithin computing device 300 during operation. Storage device 308, insome examples, is described as a computer-readable storage medium. Insome examples, storage device 308 is a temporary memory, meaning that aprimary purpose of storage device 308 is not long-term storage. Storagedevice 308, in some examples, is described as a volatile memory, meaningthat storage device 308 does not maintain stored contents when thecomputer is turned off. Examples of volatile memories include randomaccess memories (RAM), dynamic random access memories (DRAM), staticrandom access memories (SRAM), and other forms of volatile memoriesknown in the art. In some examples, storage device 308 is used to storeprogram instructions for execution by processors 302. Storage device308, in one example, is used by software or applications running oncomputing device 300 to temporarily store information during programexecution.

Storage devices 308, in some examples, also include one or morecomputer-readable storage media. Storage devices 308 may be configuredto store larger amounts of information than volatile memory. Storagedevices 308 may further be configured for long-term storage ofinformation. In some examples, storage devices 308 include non-volatilestorage elements. Examples of such non-volatile storage elements includemagnetic hard discs, optical discs, floppy discs, flash memories, orforms of electrically programmable memories (EPROM) or electricallyerasable and programmable (EEPROM) memories.

Computing device 300, in some examples, also includes one or morecommunication units 306. Computing device 300, in one example, utilizescommunication unit 306 to communicate with external devices via one ormore networks, such as one or more wireless networks. Communication unit306 may be a network interface card, such as an Ethernet card, anoptical transceiver, a radio frequency transceiver, or any other type ofdevice that can send and receive information. Other examples of suchnetwork interfaces may include Bluetooth, 3G and WiFi radios computingdevices as well as Universal Serial Bus (USB). In some examples,computing device 300 utilizes communication unit 306 to wirelesslycommunicate with an external device such as a server (e.g., remotesystem 118 of FIGS. 1, 2A, and 2B).

In addition, the computing device 300 may include short-range wirelesscommunication module 326. As described herein, short-range wirelesscommunication module 326 may be active hardware that is configured tocommunicate with other short-range communication devices. In general,short-range wireless communication module 326 may be configured tocommunicate wirelessly with other devices in physical proximity toshort-range wireless communication module 326 (e.g., less thanapproximately ten centimeters, or less than approximately fourcentimeters), such as tag device 114 of FIGS. 1, 2A, and 2B. In someexamples, short-range communication module 326 may include a near-fieldcommunication (NFC) module that communicates via NFC. In other examplesshort-range wireless communication module 326 may be replaced with analternative short-range communication device configured to communicatewith and receive data from other short range communication sensors.These alternative short-range communication devices may operateaccording to Bluetooth, Ultra-Wideband radio, or other similarprotocols. In some examples, short-range wireless communication module326 may be an external hardware module that is coupled with computingdevice 300 via a bus (such as via a Universal Serial Bus (USB) port).Short-range wireless communication module 326, in some examples, mayalso include software which may, in some examples, be independent fromoperating system 316, and which may, in some other examples, be asub-routine of operating system 316.

Computing device 300, in one example, also includes one or more inputdevices 304. Input device 304, in some examples, is configured toreceive input from a user through tactile, audio, or video feedback.Examples of input device 304 include a presence-sensitive display, amouse, a keyboard, a voice responsive system, video camera, microphoneor any other type of device for detecting a command from a user. In someexamples, a presence-sensitive display includes a touch-sensitivescreen.

One or more output devices 312 may also be included in computing device300. Output device 312, in some examples, is configured to provideoutput to a user using tactile, audio, or video stimuli. Output device312, in one example, includes a presence-sensitive display, a soundcard, a video graphics adapter card, or any other type of device forconverting a signal into an appropriate form understandable to humans ormachines. Additional examples of output device 312 include a speaker, acathode ray tube (CRT) monitor, a liquid crystal display (LCD), or anyother type of device that can generate intelligible output to a user. Insome examples, user interface (UI) device 310 may include functionalityof input device 304 and/or output device 312. In the example of FIGS. 1,2A, and 2B, UI device 312 may be a presence-sensitive display.

Computing device 300 may include operating system 316. Operating system316, in some examples, controls the operation of components of computingdevice 300. For example, operating system 316, in one example,facilitates the communication of user interface device module 318,authorization module 320, and application 322 with processors 302,communication unit 306, storage device 308, input device 304, userinterface device 310, short-range wireless communication module 326, andoutput device 312. UI module 318, authorization module 320, andapplication 322 may also include program instructions and/or data thatare executable by computing device 300. As one example, modules 318,320, and 322 may include instructions that cause computing device 300 toperform one or more of the operations and actions described in thepresent disclosure. For instance, application 322 may cause computingdevice 300 to receive, by short-range wireless communication and from aclient device, a request to authorize an authorization flow and to senda corresponding authorization grant to an authorization service. Inaddition, application 322 may relay an access token received from theauthorization service to the client device by short-range wirelesscommunication.

User interface device module 318 may display a prompt at user interfacedevice 310, such as a presence-sensitive screen, in response to anauthorization request received by short-range wireless communicationdevice 326 and initiated by a client device. The prompt may provide theoption to grant or reject the authorization request. If a user grantsthe authorization request, authorization module 320 may interface withan authorization service, such as authorization service 122 of FIGS. 1,2A, and 2B, to authenticate the user and to authorize the client toaccess resources owned by the user and served by a resource service. Anyof user interface module 318, authorization module 320, and application322 may represent a web browser or web browser module.

FIGS. 5A-5C depict a flow chart illustrating an example process that maybe performed by a computing system to authorize a client device toaccess resources owned by a user and served by a resource service,according to techniques of the present disclosure. The process includesinvoking a prompt 116, by a client device 110, to prompt user 132 ofcomputing device 100 to engage tag device 114 using computing device 100(500). User 132 may locate computing device 100 within a defined rangeof tag device 114, which causes computing device 100 to engage tagdevice 114 (502). Upon tag device 114 of client device 110 detectingcomputing device 100 within the defined range, client device 110 sendsauthorization request 130 to computing device 100 using short-rangewireless communication provided by tag device 114 by communication path126 (504).

Computing device 100 receives authorization request 130 (506) anddisplays prompt 104 to request authorization by user 132 to proceed withthe authorization for client device 110 (508). If user 132 fails toauthorize (NO branch of 510), computing device 100 may send anauthorization reject message to client device 100 (512), which receivesthe authorization reject message (514). If user 132 accepts andauthorizes computing device 100 to proceed (YES branch of 510), theprocess may proceed according to relay mode or direct mode (516).

In general, in accordance with relay mode (YES branch of 516), computingdevice 100 relays an access token 402 to client device 110. Morespecifically, in the example process illustrated by FIG. 5B, computingdevice 100 sends authorization grant 400 to an authorization service 122of remote system 118 (518). Authorization grant 400 may include resourceowner credentials for user 132. Authorization service 122 receivesauthorization grant 400 (520) and, in some instances, authenticates user132 (522). In addition, authorization service 122 provides authorizationcorresponding to authorization request 130 by generating access token402 that grants access to a requested resource hosted by resourceservice 120 (523). Authorization service 122 sends access token 402 tocomputing device 100 (524), which receives access token 402 (526) andsends access token 402 to client device 110 using short-range wirelesscommunication by communication pathway 126 (528). Client device 110receives access token 402 (530).

Client device 110 may include access token 402 in a resource request toresource service 120 of remote system 118 (532). Remote system 118receives the resource request (534). Upon validating access token 402,remote system 118 provides access to client device 110 to the requestedresource (536).

In general, in accordance with direct mode (NO branch of 516),authorization service 122 sends an access token 412 directly to clientdevice 110. More specifically, in the example process illustrated byFIG. 5C, computing device 100 sends authorization grant 410 to anauthorization service 122 of remote system 118 (540). Authorizationgrant 412 may include resource owner credentials for user 132.Authorization service 122 receives authorization grant 400 (542) and, insome instances, authenticates user 132 (543). In addition, authorizationservice 122 provides authorization corresponding to authorizationrequest 130 by generating access token 412 that grants access to arequested resource hosted by resource service 120 (544). Authorizationservice 122 sends access token 412 directly to client device 110 bycommunication pathway 124 (546). Client device 110 receives access token402 (548).

Client device 110 may include access token 412 in a resource request toresource service 120 of remote system 118 (550). Remote system 118receives the resource request (552). Upon validating access token 412,remote system 118 provides access to client device 110 to the requestedresource (554).

FIG. 6 is a flow chart illustrating an example process that may beperformed by a computing system to authorize a client device to accessresources owned by a user and served by a resource service, according totechniques of the present disclosure. The process includes receiving, bycomputing device 100 and using short-range wireless communication, anauthentication request 130 from client device 110 (602). Computingdevice 100 receives, at an input device operably coupled to computingdevice 100, such as display 102, authorization to provide a securitycredential to client device 110 (604). In response to receiving theauthorization, computing device 100 sends an indication of theauthorization, such as authorization grant 400 of FIG. 2A orauthorization grant 410 of FIG. 2B, to authorization service 122 (606).

The techniques described in this disclosure may be implemented, at leastin part, in hardware, software, firmware, or any combination thereof.For example, various aspects of the described techniques may beimplemented within one or more processors, including one or moremicroprocessors, digital signal processors (DSPs), application specificintegrated circuits (ASICs), field programmable gate arrays (FPGAs), orany other equivalent integrated or discrete logic circuitry, as well asany combinations of such components. The term “processor” or “processingcircuitry” may generally refer to any of the foregoing logic circuitry,alone or in combination with other logic circuitry, or any otherequivalent circuitry. A control unit including hardware may also performone or more of the techniques of this disclosure.

Such hardware, software, and firmware may be implemented within the samedevice or within separate devices to support the various techniquesdescribed in this disclosure. In addition, any of the described units,modules or components may be implemented together or separately asdiscrete but interoperable logic devices. Depiction of differentfeatures as modules or units is intended to highlight differentfunctional aspects and does not necessarily imply that such modules orunits must be realized by separate hardware, firmware, or softwarecomponents. Rather, functionality associated with one or more modules orunits may be performed by separate hardware, firmware, or softwarecomponents, or integrated within common or separate hardware, firmware,or software components.

The techniques described in this disclosure may also be embodied orencoded in an article of manufacture including a computer-readablestorage medium encoded with instructions. Instructions embedded orencoded in an article of manufacture including a computer-readablestorage medium encoded, may cause one or more programmable processors,or other processors, to implement one or more of the techniquesdescribed herein, such as when instructions included or encoded in thecomputer-readable storage medium are executed by the one or moreprocessors. Computer readable storage media may include random accessmemory (RAM), read only memory (ROM), programmable read only memory(PROM), erasable programmable read only memory (EPROM), electronicallyerasable programmable read only memory (EEPROM), flash memory, a harddisk, a compact disc ROM (CD-ROM), a floppy disk, a cassette, magneticmedia, optical media, or other computer readable storage media.

In some examples, a computer-readable storage medium may comprisenon-transitory medium. The term “non-transitory” may indicate that thestorage medium is not embodied in a carrier wave or a propagated signal.In certain examples, a non-transitory storage medium may store data thatcan, over time, change (e.g., in RAM or cache).

Various examples of the disclosure have been described. These and otherexamples are within the scope of the following claims.

1-20. (canceled)
 21. A method comprising: receiving, by a mobilecomputing device from a client device and using short-range wirelesscommunication, an authorization request for authorization to exchangeinformation with a resource service that hosts a protected resource;receiving, at an input device operably coupled to the mobile computingdevice, authorization to provide at least one security credential to theclient device; and sending, by the mobile computing device to anauthorization service and in response to receiving the authorization, anindication of the authorization to provide at least one securitycredential to the client device.
 22. The method of claim 21, furthercomprising: prior to receiving the authorization request from the clientdevice, establishing, by the mobile computing device and with the clientdevice, a short-range wireless communication pathway, wherein receivingthe authorization request comprises receiving, by the mobile computingdevice from the client device via the short-range wireless communicationpathway, the authorization request.
 23. The method of claim 21, furthercomprising: receiving, by the mobile computing device and from theauthorization service, the at least one security credential, wherein theat least one security credential provides the client device with accessto exchange information with the resource service that hosts theprotected resource associated with the at least one security credential;and responsive to receiving the at least one security credential,sending, by the mobile computing device, the at least one securitycredential to the client device.
 24. The method of claim 23, whereinsending, by the mobile computing device, the at least one securitycredential to the client device comprises sending the at least onesecurity credential to the client device using a short-range wirelesscommunication pathway.
 25. The method of claim 23, wherein the protectedresource comprises one of a digital file, user profile information, anda user account.
 26. The method of claim 21, further comprising:outputting, by the mobile computing device and for display at thepresence-sensitive screen operatively coupled to the mobile computingdevice, a prompt requesting that a user grant the authorization request,wherein receiving, at the input device operably coupled to the mobilecomputing device, the authorization to provide at least one securitycredential to the client device comprises receiving the authorization atthe presence-sensitive screen.
 27. The method of claim 21, wherein theauthorization request comprises a redirection Uniform ResourceIdentifier, the method further comprising: outputting, by the mobilecomputing device and for display at a presence-sensitive screenoperatively coupled to the mobile computing device, a resourceidentified by the Uniform Resource Identifier.
 28. The method of claim21, further comprising: receiving, by the mobile computing device andfrom the authorization service, an authorization code; and responsive toreceiving the authorization code, sending, by the mobile computingdevice, the authorization code to the client device.
 29. The method ofclaim 28, wherein sending, by the mobile computing device, theauthorization code comprises sending the authorization code to theclient device via the short-range wireless communication pathway. 30.The method of claim 21, wherein the short-range wireless communicationcomprises one of Near-Field Communication and Bluetooth.
 31. A methodcomprising: sending, by a client device to a mobile computing device andusing short-range wireless communication, an authorization request forauthorization to exchange information with a resource service that hostsa protected resource; and receiving, by the client device and responsiveto the authorization request, at least one security credentialoriginated by an authorization service, wherein the at least onesecurity credential provides the client device with the authorization toexchange information with the resource service that hosts the protectedresource, the protected resource associated with the at least onesecurity credential.
 32. The method of claim 31, further comprising:presenting, by the client device, a prompt to locate the mobilecomputing device within a defined range of a tag device of the clientdevice.
 33. The method of claim 31, wherein sending, by the clientdevice and using short-range wireless communication, the authorizationrequest to the mobile computing device comprises sending theauthorization request responsive to detecting the mobile computingdevice is located within a defined range of the tag device of the clientdevice.
 34. The method of claim 31, further comprising: sending, by theclient device, the at least one security credential to the resourceservice to authorize the client device to exchange information with theresource service; and accessing, by the client device, the protectedresource.
 35. A client device comprising: at least one processor; ashort-range wireless communication unit to send, to a mobile computingdevice and using short-range wireless communication, an authorizationrequest for authorization to exchange information with a resourceservice that hosts a protected resource; and an authorization serviceinterface module operable by the at least one processor to receive,responsive to the authorization request, at least one securitycredential originated by an authorization service, wherein the at leastone security credential provides the client device with theauthorization to exchange information with the resource service thathosts the protected resource, the protected resource associated with theat least one security credential.
 36. The client device of claim 35,wherein the short-range wireless communication unit comprises a tagdevice, the client device further comprising: a user interface device;and a user interface device module operable by the at least oneprocessor to present, at the user interface device, a prompt to locatethe mobile computing device within a defined range of the tag device.37. The client device of claim 35, wherein to send the authorizationrequest to the mobile computing device the short-range wirelesscommunication unit is further operable by the at least one processor tosend the authorization request responsive to the tag device detectingthe mobile computing device is located within a defined range of the tagdevice.
 38. The client device of claim 35, further comprising: aresource service interface operable by the at least one processor tosend the at least one security credential to the resource service toauthorize the client device to exchange information with the resourceservice, wherein the resource service interface is further operable bythe at least one processor to access the protected resource.
 39. Theclient device of claim 35, wherein the at least one security credentialcomprises one of an access token and a refresh token.
 40. The clientdevice of claim 35, wherein the short-range wireless communicationcomprises one of Near-Field Communication and Bluetooth.